The SAS/CONNECT UNIX client does not initiate a Kerberos SIGNON to a SAS/CONNECT spawner when the SASCMD SAS global option is set. Instead, when the SAS option SASCMD is set, an MP Connect / SASCMD SAS session is initiated.

A temporary workaround is to clear the value specified for the SASCMD option.

Click the Hot Fix tab in this note for a link to instructions about accessing and applying the software update.

After applying the associated hot fix, you can force the Kerberos SIGNON by specifying USER=_SSPI_ in the SIGNON statement regardless of the value that is specified for SASCMD option.

Operating System and Release Information

Product Family	Product	System	Product Release		SAS Release
			Reported	Fixed*	Reported	Fixed*
SAS System	SAS/CONNECT	Solaris for x64	9.4_M7	9.4_M8	9.4 TS1M7	9.4 TS1M8
		Linux for x64	9.4_M7	9.4_M8	9.4 TS1M7	9.4 TS1M8
		HP-UX IPF	9.4_M7	9.4_M8	9.4 TS1M7	9.4 TS1M8
		64-bit Enabled Solaris	9.4_M7	9.4_M8	9.4 TS1M7	9.4 TS1M8

* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.

---

Viya on Linux: An update for this issue is available for SAS Viya 3.5. For instructions on how to access and apply software updates, see the Updating Your SAS Viya software section in the SAS Viya 3.5 for Linux Deployment Guide at

http://documentation.sas.com/?softwareId=administration&softwareVersion=3.5&softwareContextId=softwareUpdates

---

A fix for this issue for Base SAS 9.4_M7 is available at:

https://tshf.sas.com/techsup/download/hotfix/HF2/I9R.html#69105

---

To add Kerberos SIGNON support for UNIX client and to add support to force Kerberos SIGNON when SASCMD option is set

Type:	Problem Note
Priority:	medium

Date Modified:	2022-04-27 15:28:25
Date Created:	2022-04-18 23:53:34